I have no idea, why tests are failed.
There are no any helpful messages in the log.
For me it works under linux and winfows.
Could you take a look please?

Thank you.

Is there any precedent in the vim/neovim ecosystem for calling an embedded file type something like vim/lua?

If it's a custom extension I would be hesitant to merge the PR.

No conflicts with vim/nvim.
This format ("vue/htnl", etc...) is used internally only and does not passed to the editor.
It used only in the lua code to find appropriate filetypes mapping (if they were defined by the user).

I changed filetype separator to ".", this is more vim-like. This doesn't affect anything, just for consistency.

@hrsh7th
Hi, will you accept it? Tell me please if you have any questions.

Hi, man.
So, what is your decision?
Please, reject it, if you don't want this changes.

What I'm wondering is that this function is so useful and versatile that a standard mechanism will eventually be implemented in the neovim core.

In other words, if we choose ft/ft or ft.ft here and the official version chooses ft#ft, it will lose consistency.

Apart from that, I think ft/ft is better.

For now, let's merge with ft/ft.

So, should I revert separator back from "." to "/" and you will merge?

yes :)

Filetype separator reverted to "/".

thank you

Thank you!